Common channel configuration in new radio inactive state

ABSTRACT

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment may receive a radio resource control (RRC) resume message, associated with transitioning the UE from an inactive state to a connected state. The UE may configure, based at least in part on receiving the RRC resume message, the UE with a serving cell common configuration, associated with a serving cell of the UE, received in a system information block (SIB) associated with the serving cell. Numerous other aspects are provided.

CROSS REFERENCE TO RELATED APPLICATION

This application claims priority to Indian Application No. 201841043203,filed on Nov. 16, 2018, entitled “COMMON CHANNEL CONFIGURATION IN NEWRADIO INACTIVE STATE,” which is hereby expressly incorporated byreference herein.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wirelesscommunication, and to techniques and apparatuses for common channelconfiguration in New Radio (NR) inactive state.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power, and/or the like). Examples of such multiple-accesstechnologies include code division multiple access (CDMA) systems, timedivision multiple access (TDMA) systems, frequency-division multipleaccess (FDMA) systems, orthogonal frequency-division multiple access(OFDMA) systems, single-carrier frequency-division multiple access(SC-FDMA) systems, time division synchronous code division multipleaccess (TD-SCDMA) systems, and Long Term Evolution (LTE).LTE/LTE-Advanced is a set of enhancements to the Universal MobileTelecommunications System (UMTS) mobile standard promulgated by theThird Generation Partnership Project (3GPP).

A wireless communication network may include a number of base stations(BSs) that can support communication for a number of user equipment(UEs). A user equipment (UE) may communicate with a base station (BS)via the downlink and uplink. The downlink (or forward link) refers tothe communication link from the BS to the UE, and the uplink (or reverselink) refers to the communication link from the UE to the BS. As will bedescribed in more detail herein, a BS may be referred to as a Node B, agNB, an access point (AP), a radio head, a transmit receive point (TRP),a New Radio (NR) BS, a 5G Node B, and/or the like.

The above multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent user equipment to communicate on a municipal, national,regional, and even global level. New Radio (NR), which may also bereferred to as 5G, is a set of enhancements to the LTE mobile standardpromulgated by the Third Generation Partnership Project (3GPP). NR isdesigned to better support mobile broadband Internet access by improvingspectral efficiency, lowering costs, improving services, making use ofnew spectrum, and better integrating with other open standards usingorthogonal frequency division multiplexing (OFDM) with a cyclic prefix(CP) (CP-OFDM) on the downlink (DL), using CP-OFDM and/or SC-FDM (e.g.,also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) onthe uplink (UL), as well as supporting beamforming, multiple-inputmultiple-output (MIMO) antenna technology, and carrier aggregation.However, as the demand for mobile broadband access continues toincrease, there exists a need for further improvements in LTE and NRtechnologies. Preferably, these improvements should be applicable toother multiple access technologies and the telecommunication standardsthat employ these technologies.

SUMMARY

In some aspects, a method of wireless communication, performed by a userequipment (UE), may include receiving a radio resource control (RRC)resume message, associated with transitioning the UE from an inactivestate to a connected state; and configuring, based at least in part onreceiving the RRC resume message, the UE with a serving cell commonconfiguration, associated with a serving cell of the UE, received in asystem information block (SIB) associated with the serving cell.

In some aspects, a UE for wireless communication may include memory andone or more processors coupled to the memory. The memory and the one ormore processors may be configured to receive a RRC resume message,associated with transitioning the UE from an inactive state to aconnected state; and configure, based at least in part on receiving theRRC resume message, the UE with a serving cell common configuration,associated with a serving cell of the UE, received in a SIB associatedwith the serving cell.

In some aspects, a non-transitory computer-readable medium may store oneor more instructions for wireless communication. The one or moreinstructions, when executed by one or more processors of a UE, may causethe one or more processors to receive a RRC resume message, associatedwith transitioning the UE from an inactive state to a connected state;and configure, based at least in part on receiving the RRC resumemessage, the UE with a serving cell common configuration, associatedwith a serving cell of the UE, received in a SIB associated with theserving cell.

In some aspects, an apparatus for wireless communication may includemeans for receiving a RRC resume message, associated with transitioningthe apparatus from an inactive state to a connected state; and means forconfiguring, based at least in part on receiving the RRC resume message,the apparatus with a serving cell common configuration, associated witha serving cell of the apparatus, received in a SIB associated with theserving cell.

Aspects generally include a method, apparatus, system, computer programproduct, non-transitory computer-readable medium, user equipment, basestation, wireless communication device, and/or processing system assubstantially described herein with reference to and as illustrated bythe accompanying drawings and specification.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. Each of the figures is provided for the purpose ofillustration and description, and not as a definition of the limits ofthe claims.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can beunderstood in detail, a more particular description, briefly summarizedabove, may be had by reference to aspects, some of which are illustratedin the appended drawings. It should be noted, however, that the appendeddrawings illustrate only certain typical aspects of this disclosure andare therefore not to be considered limiting of its scope, for thedescription may admit to other equally effective aspects. The samereference numbers in different drawings may identify the same or similarelements.

FIG. 1 is a block diagram conceptually illustrating an example of awireless communication network, in accordance with various aspects ofthe present disclosure.

FIG. 2 is a block diagram conceptually illustrating an example of a basestation in communication with a user equipment (UE) in a wirelesscommunication network, in accordance with various aspects of the presentdisclosure.

FIG. 3A is a block diagram conceptually illustrating an example of aframe structure in a wireless communication network, in accordance withvarious aspects of the present disclosure.

FIG. 3B is a block diagram conceptually illustrating an examplesynchronization communication hierarchy in a wireless communicationnetwork, in accordance with various aspects of the present disclosure.

FIG. 4 is a block diagram conceptually illustrating an example slotformat with a normal cyclic prefix, in accordance with various aspectsof the present disclosure.

FIGS. 5A and 5B are diagrams illustrating examples of common channelconfiguration in New Radio (NR) inactive state, in accordance withvarious aspects of the present disclosure.

FIG. 6 is a diagram illustrating an example process performed, forexample, by a user equipment, in accordance with various aspects of thepresent disclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafterwith reference to the accompanying drawings. This disclosure may,however, be embodied in many different forms and should not be construedas limited to any specific structure or function presented throughoutthis disclosure. Rather, these aspects are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the disclosure to those skilled in the art. Based on theteachings herein one skilled in the art should appreciate that the scopeof the disclosure is intended to cover any aspect of the disclosuredisclosed herein, whether implemented independently of or combined withany other aspect of the disclosure. For example, an apparatus may beimplemented or a method may be practiced using any number of the aspectsset forth herein. In addition, the scope of the disclosure is intendedto cover such an apparatus or method which is practiced using otherstructure, functionality, or structure and functionality in addition toor other than the various aspects of the disclosure set forth herein. Itshould be understood that any aspect of the disclosure disclosed hereinmay be embodied by one or more elements of a claim.

Several aspects of telecommunication systems will now be presented withreference to various apparatuses and techniques. These apparatuses andtechniques will be described in the following detailed description andillustrated in the accompanying drawings by various blocks, modules,components, circuits, steps, processes, algorithms, and/or the like(collectively referred to as “elements”). These elements may beimplemented using hardware, software, or combinations thereof. Whethersuch elements are implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem.

It should be noted that while aspects may be described herein usingterminology commonly associated with 3G and/or 4G wireless technologies,aspects of the present disclosure can be applied in othergeneration-based communication systems, such as 5G and later, includingNR technologies.

FIG. 1 is a diagram illustrating a network 100 in which aspects of thepresent disclosure may be practiced. The network 100 may be an LTEnetwork or some other wireless network, such as a 5G or NR network.Wireless network 100 may include a number of BSs 110 (shown as BS 110 a,BS 110 b, BS 110 c, and BS 110 d) and other network entities. A BS is anentity that communicates with user equipment (UEs) and may also bereferred to as a base station, an NR BS, a Node B, a gNB, a 5G node B(NB), an access point, a transmit receive point (TRP), and/or the like.Each BS may provide communication coverage for a particular geographicarea. In 3GPP, the term “cell” can refer to a coverage area of a BSand/or a BS subsystem serving this coverage area, depending on thecontext in which the term is used.

A BS may provide communication coverage for a macro cell, a pico cell, afemto cell, and/or another type of cell. A macro cell may cover arelatively large geographic area (e.g., several kilometers in radius)and may allow unrestricted access by UEs with service subscription. Apico cell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femto cell maycover a relatively small geographic area (e.g., a home) and may allowrestricted access by UEs having association with the femto cell (e.g.,UEs in a closed subscriber group (CSG)). A BS for a macro cell may bereferred to as a macro BS. A BS for a pico cell may be referred to as apico BS. A BS for a femto cell may be referred to as a femto BS or ahome BS. In the example shown in FIG. 1, a BS 110 a may be a macro BSfor a macro cell 102 a, a BS 110 b may be a pico BS for a pico cell 102b, and a BS 110 c may be a femto BS for a femto cell 102 c. A BS maysupport one or multiple (e.g., three) cells. The terms “eNB”, “basestation”, “NR BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB”, and “cell” maybe used interchangeably herein.

In some aspects, a cell may not necessarily be stationary, and thegeographic area of the cell may move according to the location of amobile BS. In some aspects, the BSs may be interconnected to one anotherand/or to one or more other BSs or network nodes (not shown) in theaccess network 100 through various types of backhaul interfaces such asa direct physical connection, a virtual network, and/or the like usingany suitable transport network.

Wireless network 100 may also include relay stations. A relay station isan entity that can receive a transmission of data from an upstreamstation (e.g., a BS or a UE) and send a transmission of the data to adownstream station (e.g., a UE or a BS). A relay station may also be aUE that can relay transmissions for other UEs. In the example shown inFIG. 1, a relay station 110 d may communicate with macro BS 110 a and aUE 120 d in order to facilitate communication between BS 110 a and UE120 d. A relay station may also be referred to as a relay BS, a relaybase station, a relay, and/or the like.

Wireless network 100 may be a heterogeneous network that includes BSs ofdifferent types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, and/orthe like. These different types of BSs may have different transmit powerlevels, different coverage areas, and different impacts on interferencein wireless network 100. For example, macro BSs may have a high transmitpower level (e.g., 5 to 40 Watts) whereas pico BSs, femto BSs, and relayBSs may have lower transmit power levels (e.g., 0.1 to 2 Watts).

A network controller 130 may couple to a set of BSs and may providecoordination and control for these BSs. Network controller 130 maycommunicate with the BSs via a backhaul. The BSs may also communicatewith one another, e.g., directly or indirectly via a wireless orwireline backhaul.

UEs 120 (e.g., 120 a, 120 b, 120 c) may be dispersed throughout wirelessnetwork 100, and each UE may be stationary or mobile. A UE may also bereferred to as an access terminal, a terminal, a mobile station, asubscriber unit, a station, and/or the like. A UE may be a cellularphone (e.g., a smart phone), a personal digital assistant (PDA), awireless modem, a wireless communication device, a handheld device, alaptop computer, a cordless phone, a wireless local loop (WLL) station,a tablet, a camera, a gaming device, a netbook, a smartbook, anultrabook, a medical device or equipment, biometric sensors/devices,wearable devices (smart watches, smart clothing, smart glasses, smartwrist bands, smart jewelry (e.g., smart ring, smart bracelet)), anentertainment device (e.g., a music or video device, or a satelliteradio), a vehicular component or sensor, smart meters/sensors,industrial manufacturing equipment, a global positioning system device,or any other suitable device that is configured to communicate via awireless or wired medium.

Some UEs may be considered machine-type communication (MTC) or evolvedor enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEsinclude, for example, robots, drones, remote devices, sensors, meters,monitors, location tags, and/or the like, that may communicate with abase station, another device (e.g., remote device), or some otherentity. A wireless node may provide, for example, connectivity for or toa network (e.g., a wide area network such as Internet or a cellularnetwork) via a wired or wireless communication link. Some UEs may beconsidered Internet-of-Things (IoT) devices, and/or may be implementedas NB-IoT (narrowband internet of things) devices. Some UEs may beconsidered a Customer Premises Equipment (CPE). UE 120 may be includedinside a housing that houses components of UE 120, such as processorcomponents, memory components, and/or the like.

In general, any number of wireless networks may be deployed in a givengeographic area. Each wireless network may support a particular RAT andmay operate on one or more frequencies. A RAT may also be referred to asa radio technology, an air interface, and/or the like. A frequency mayalso be referred to as a carrier, a frequency channel, and/or the like.Each frequency may support a single RAT in a given geographic area inorder to avoid interference between wireless networks of different RATs.In some cases, NR or 5G RAT networks may be deployed.

In some aspects, two or more UEs 120 (e.g., shown as UE 120 a and UE 120e) may communicate directly using one or more sidelink channels (e.g.,without using a base station 110 as an intermediary to communicate withone another). For example, the UEs 120 may communicate usingpeer-to-peer (P2P) communications, device-to-device (D2D)communications, a vehicle-to-everything (V2X) protocol (e.g., which mayinclude a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure(V2I) protocol, and/or the like), a mesh network, and/or the like. Inthis case, the UE 120 may perform scheduling operations, resourceselection operations, and/or other operations described elsewhere hereinas being performed by the base station 110.

As indicated above, FIG. 1 is provided merely as an example. Otherexamples may differ from what is described with regard to FIG. 1.

FIG. 2 shows a block diagram of a design 200 of base station 110 and UE120, which may be one of the base stations and one of the UEs in FIG. 1.Base station 110 may be equipped with T antennas 234 a through 234 t,and UE 120 may be equipped with R antennas 252 a through 252 r, where ingeneral T≥1 and R≥1.

At base station 110, a transmit processor 220 may receive data from adata source 212 for one or more UEs, select one or more modulation andcoding schemes (MCS) for each UE based at least in part on channelquality indicators (CQIs) received from the UE, process (e.g., encodeand modulate) the data for each UE based at least in part on the MCS(s)selected for the UE, and provide data symbols for all UEs. Transmitprocessor 220 may also process system information (e.g., for semi-staticresource partitioning information (SRPI) and/or the like) and controlinformation (e.g., CQI requests, grants, upper layer signaling, and/orthe like) and provide overhead symbols and control symbols. Transmitprocessor 220 may also generate reference symbols for reference signals(e.g., the cell-specific reference signal (CRS)) and synchronizationsignals (e.g., the primary synchronization signal (PSS) and secondarysynchronization signal (SSS)). A transmit (TX) multiple-inputmultiple-output (MIMO) processor 230 may perform spatial processing(e.g., precoding) on the data symbols, the control symbols, the overheadsymbols, and/or the reference symbols, if applicable, and may provide Toutput symbol streams to T modulators (MODs) 232 a through 232 t. Eachmodulator 232 may process a respective output symbol stream (e.g., forOFDM and/or the like) to obtain an output sample stream. Each modulator232 may further process (e.g., convert to analog, amplify, filter, andupconvert) the output sample stream to obtain a downlink signal. Tdownlink signals from modulators 232 a through 232 t may be transmittedvia T antennas 234 a through 234 t, respectively. According to variousaspects described in more detail below, the synchronization signals canbe generated with location encoding to convey additional information.

At UE 120, antennas 252 a through 252 r may receive the downlink signalsfrom base station 110 and/or other base stations and may providereceived signals to demodulators (DEMODs) 254 a through 254 r,respectively. Each demodulator 254 may condition (e.g., filter, amplify,downconvert, and digitize) a received signal to obtain input samples.Each demodulator 254 may further process the input samples (e.g., forOFDM and/or the like) to obtain received symbols. A MIMO detector 256may obtain received symbols from all R demodulators 254 a through 254 r,perform MIMO detection on the received symbols if applicable, andprovide detected symbols. A receive processor 258 may process (e.g.,demodulate and decode) the detected symbols, provide decoded data for UE120 to a data sink 260, and provide decoded control information andsystem information to a controller/processor 280. A channel processormay determine reference signal received power (RSRP), received signalstrength indicator (RSSI), reference signal received quality (RSRQ),channel quality indicator (CQI), and/or the like. In some aspects, oneor more components of UE 120 may be included in a housing.

On the uplink, at UE 120, a transmit processor 264 may receive andprocess data from a data source 262 and control information (e.g., forreports comprising RSRP, RSSI, RSRQ, CQI, and/or the like) fromcontroller/processor 280. Transmit processor 264 may also generatereference symbols for one or more reference signals. The symbols fromtransmit processor 264 may be precoded by a TX MIMO processor 266 ifapplicable, further processed by modulators 254 a through 254 r (e.g.,for DFT-s-OFDM, CP-OFDM, and/or the like), and transmitted to basestation 110. At base station 110, the uplink signals from UE 120 andother UEs may be received by antennas 234, processed by demodulators232, detected by a MIMO detector 236 if applicable, and furtherprocessed by a receive processor 238 to obtain decoded data and controlinformation sent by UE 120. Receive processor 238 may provide thedecoded data to a data sink 239 and the decoded control information tocontroller/processor 240. Base station 110 may include communicationunit 244 and communicate to network controller 130 via communicationunit 244. Network controller 130 may include communication unit 294,controller/processor 290, and memory 292.

Controller/processor 240 of base station 110, controller/processor 280of UE 120, and/or any other component(s) of FIG. 2 may perform one ormore techniques associated with common channel configuration in NRinactive state, as described in more detail elsewhere herein. Forexample, controller/processor 240 of base station 110,controller/processor 280 of UE 120, and/or any other component(s) ofFIG. 2 may perform or direct operations of, for example, process 600 ofFIG. 6 and/or other processes as described herein. Memories 242 and 282may store data and program codes for base station 110 and UE 120,respectively. A scheduler 246 may schedule UEs for data transmission onthe downlink and/or uplink.

In some aspects, UE 120 may include means for receiving a RRC resumemessage, associated with transitioning UE 120 from an inactive state toa connected state; means for configuring, based at least in part onreceiving the RRC resume message, UE 120 with a serving cell commonconfiguration, associated with a serving cell of UE 120, received in aSIB associated with the serving cell; and/or the like. In some aspects,such means may include one or more components of UE 120 described inconnection with FIG. 2.

As indicated above, FIG. 2 is provided merely as an example. Otherexamples may differ from what is described with regard to FIG. 2.

FIG. 3A shows an example frame structure 300 for frequency divisionduplexing (FDD) in a telecommunications system (e.g., NR). Thetransmission timeline for each of the downlink and uplink may bepartitioned into units of radio frames (sometimes referred to asframes). Each radio frame may have a predetermined duration (e.g., 10milliseconds (ms)) and may be partitioned into a set of Z (Z≥1)subframes (e.g., with indices of 0 through Z−1). Each subframe may havea predetermined duration (e.g., 1 ms) and may include a set of slots(e.g., 2^(m) slots per subframe are shown in FIG. 3A, where m is anumerology used for a transmission, such as 0, 1, 2, 3, 4, and/or thelike). Each slot may include a set of L symbol periods. For example,each slot may include fourteen symbol periods (e.g., as shown in FIG.3A), seven symbol periods, or another number of symbol periods. In acase where the subframe includes two slots (e.g., when m=1), thesubframe may include 2L symbol periods, where the 2L symbol periods ineach subframe may be assigned indices of 0 through 2L−1. In someaspects, a scheduling unit for the FDD may be frame-based,subframe-based, slot-based, symbol-based, and/or the like.

While some techniques are described herein in connection with frames,subframes, slots, and/or the like, these techniques may equally apply toother types of wireless communication structures, which may be referredto using terms other than “frame,” “subframe,” “slot,” and/or the likein 5G NR. In some aspects, a wireless communication structure may referto a periodic time-bounded communication unit defined by a wirelesscommunication standard and/or protocol. Additionally, or alternatively,different configurations of wireless communication structures than thoseshown in FIG. 3A may be used.

In certain telecommunications (e.g., NR), a base station may transmitsynchronization signals. For example, a base station may transmit aprimary synchronization signal (PSS), a secondary synchronization signal(SSS), and/or the like, on the downlink for each cell supported by thebase station. The PSS and SSS may be used by UEs for cell search andacquisition. For example, the PSS may be used by UEs to determine symboltiming, and the SSS may be used by UEs to determine a physical cellidentifier, associated with the base station, and frame timing. The basestation may also transmit a physical broadcast channel (PBCH). The PBCHmay carry some system information, such as system information thatsupports initial access by UEs.

In some aspects, the base station may transmit the PSS, the SSS, and/orthe PBCH in accordance with a synchronization communication hierarchy(e.g., a synchronization signal (SS) hierarchy) including multiplesynchronization communications (e.g., SS blocks), as described below inconnection with FIG. 3B.

FIG. 3B is a block diagram conceptually illustrating an example SShierarchy, which is an example of a synchronization communicationhierarchy. As shown in FIG. 3B, the SS hierarchy may include an SS burstset, which may include a plurality of SS bursts (identified as SS burst0 through SS burst B−1, where B is a maximum number of repetitions ofthe SS burst that may be transmitted by the base station). As furthershown, each SS burst may include one or more SS blocks (identified as SSblock 0 through SS block (b_(max_SS)−1), where b_(max_SS)−1 is a maximumnumber of SS blocks that can be carried by an SS burst). In someaspects, different SS blocks may be beam-formed differently. An SS burstset may be periodically transmitted by a wireless node, such as every Xmilliseconds, as shown in FIG. 3B. In some aspects, an SS burst set mayhave a fixed or dynamic length, shown as Y milliseconds in FIG. 3B.

The SS burst set shown in FIG. 3B is an example of a synchronizationcommunication set, and other synchronization communication sets may beused in connection with the techniques described herein. Furthermore,the SS block shown in FIG. 3B is an example of a synchronizationcommunication, and other synchronization communications may be used inconnection with the techniques described herein.

In some aspects, an SS block includes resources that carry the PSS, theSSS, the PBCH, and/or other synchronization signals (e.g., a tertiarysynchronization signal (TSS)) and/or synchronization channels. In someaspects, multiple SS blocks are included in an SS burst, and the PSS,the SSS, and/or the PBCH may be the same across each SS block of the SSburst. In some aspects, a single SS block may be included in an SSburst. In some aspects, the SS block may be at least four symbol periodsin length, where each symbol carries one or more of the PSS (e.g.,occupying one symbol), the SSS (e.g., occupying one symbol), and/or thePBCH (e.g., occupying two symbols).

In some aspects, the symbols of an SS block are consecutive, as shown inFIG. 3B. In some aspects, the symbols of an SS block arenon-consecutive. Similarly, in some aspects, one or more SS blocks ofthe SS burst may be transmitted in consecutive radio resources (e.g.,consecutive symbol periods) during one or more slots. Additionally, oralternatively, one or more SS blocks of the SS burst may be transmittedin non-consecutive radio resources.

In some aspects, the SS bursts may have a burst period, whereby the SSblocks of the SS burst are transmitted by the base station according tothe burst period. In other words, the SS blocks may be repeated duringeach SS burst. In some aspects, the SS burst set may have a burst setperiodicity, whereby the SS bursts of the SS burst set are transmittedby the base station according to the fixed burst set periodicity. Inother words, the SS bursts may be repeated during each SS burst set.

The base station may transmit system information, such as systeminformation blocks (SIBs) on a physical downlink shared channel (PDSCH)in certain slots. The base station may transmit control information/dataon a physical downlink control channel (PDCCH) in C symbol periods of aslot, where B may be configurable for each slot. The base station maytransmit traffic data and/or other data on the PDSCH in the remainingsymbol periods of each slot.

As indicated above, FIGS. 3A and 3B are provided as examples. Otherexamples may differ from what is described with regard to FIGS. 3A and3B.

FIG. 4 shows an example slot format 410 with a normal cyclic prefix. Theavailable time frequency resources may be partitioned into resourceblocks. Each resource block may cover a set of subcarriers (e.g., 12subcarriers) in one slot and may include a number of resource elements.Each resource element may cover one subcarrier in one symbol period(e.g., in time) and may be used to send one modulation symbol, which maybe a real or complex value.

An interlace structure may be used for each of the downlink and uplinkfor FDD in certain telecommunications systems (e.g., NR). For example, Qinterlaces with indices of 0 through Q−1 may be defined, where Q may beequal to 4, 6, 8, 10, or some other value. Each interlace may includeslots that are spaced apart by Q frames. In particular, interlace q mayinclude slots q, q+Q, q+2Q, etc., where q∈{0, . . . , Q−1}.

A UE may be located within the coverage of multiple BSs. One of theseBSs may be selected to serve the UE. The serving BS may be selectedbased at least in part on various criteria such as received signalstrength, received signal quality, path loss, and/or the like. Receivedsignal quality may be quantified by a signal-to-interference plus noiseratio (SINR), or a reference signal received quality (RSRQ), or someother metric. The UE may operate in a dominant interference scenario inwhich the UE may observe high interference from one or more interferingBSs.

While aspects of the examples described herein may be associated with NRor 5G technologies, aspects of the present disclosure may be applicablewith other wireless communication systems. New Radio (NR) may refer toradios configured to operate according to a new air interface (e.g.,other than Orthogonal Frequency Divisional Multiple Access (OFDMA)-basedair interfaces) or fixed transport layer (e.g., other than InternetProtocol (IP)). In aspects, NR may utilize OFDM with a CP (hereinreferred to as cyclic prefix OFDM or CP-OFDM) and/or SC-FDM on theuplink, may utilize CP-OFDM on the downlink and include support forhalf-duplex operation using time division duplexing (TDD). In aspects,NR may, for example, utilize OFDM with a CP (herein referred to asCP-OFDM) and/or discrete Fourier transform spread orthogonalfrequency-division multiplexing (DFT-s-OFDM) on the uplink, may utilizeCP-OFDM on the downlink and include support for half-duplex operationusing TDD. NR may include Enhanced Mobile Broadband (eMBB) servicetargeting wide bandwidth (e.g., 80 megahertz (MHz) and beyond),millimeter wave (mmW) targeting high carrier frequency (e.g., 60gigahertz (GHz)), massive MTC (mMTC) targeting non-backward compatibleMTC techniques, and/or mission critical targeting ultra reliable lowlatency communications (URLLC) service.

In some aspects, a single component carrier bandwidth of 100 MHz may besupported. NR resource blocks may span 12 sub-carriers with asub-carrier bandwidth of 60 or 120 kilohertz (kHz) over a 0.1millisecond (ms) duration. Each radio frame may include 40 slots and mayhave a length of 10 ms. Consequently, each slot may have a length of0.25 ms. Each slot may indicate a link direction (e.g., DL or UL) fordata transmission and the link direction for each slot may bedynamically switched. Each slot may include DL/UL data as well as DL/ULcontrol data.

Beamforming may be supported and beam direction may be dynamicallyconfigured. MIMO transmissions with precoding may also be supported.MIMO configurations in the DL may support up to 8 transmit antennas withmulti-layer DL transmissions up to 8 streams and up to 2 streams per UE.Multi-layer transmissions with up to 2 streams per UE may be supported.Aggregation of multiple cells may be supported with up to 8 servingcells. Alternatively, NR may support a different air interface, otherthan an OFDM-based interface. NR networks may include entities such ascentral units or distributed units.

As indicated above, FIG. 4 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 4.

In an NR network, a UE may operate in a connected state (e.g., a radioresource control (RRC) connected mode), an idle state (e.g., an RRC idlemode), or an inactive state (e.g., RRC inactive mode). When the UE ispowered-on, the UE is in the idle state, and the UE can transition tothe connected state (e.g., with an initial attachment to the network,with establishment of a network connection, and/or the like). If thereis no activity from the UE for a threshold amount of time, the servingcell of the UE can suspend the UE session and trigger the UE totransition to the inactive state.

As part of the transition to the inactive state, both the UE and thenetwork (e.g., a base station associated with the serving cell) store anaccess stratum (AS) context associated with the UE. The AS contextincludes, for example, a current RRC configuration, a current securitycontext, a packet data convergence protocol (PDCP) state (including arobust header compression (ROHC) state), a service data adaptationprotocol (SDAP) configuration, a cell radio network temporary identifier(C-RNTI) used in a primary cell, a cell identity, a physical cellidentity of a primary cell, and/or the like. As described below, thestoring of the AS context eliminates a need for such information to bere-provided to the UE when the UE transitions back to the connectedstate from the inactive state.

While in the inactive state, the UE handles mobility (e.g., such thatthe UE can be reselected to another serving cell while in the inactivestate or can move to another serving cell while in the active state).Thus, the serving cell of the UE can change while the UE is in theinactive state.

The UE can detect a trigger, associated with resuming the session, when,for example, the UE needs to transmit an uplink transmission, when theUE detects a paging message for the UE, and/or the like. Here, the UEcan trigger a resume procedure, associated with resuming the session, bysending a resume request (e.g., an RRC resume request) to the currentserving cell of the UE. In a case in which the UE switches to (e.g., isreselected to, moves to, and/or the like) another serving cell while inthe inactive mode, the resume request is transmitted using a servingcell common configuration associated with the new serving cell, which isread from a system information block (SIB) (e.g., SIB1) of the newserving cell as a result of the reselection to the new serving cell.

Next, the UE receives a resume message (e.g., an RRC resume message)associated with resuming the session, which triggers the UE totransition from the inactive state to the connected state. Based on thistrigger, the UE restores the AS context using the AS context stored onthe UE. Here, restoration of the AS context may reduce an amount of timeneeded to transition to the connected state and may reduce signalingoverhead (e.g., as compared to transitioning to the connected state fromthe idle state) since information included in the AS context need not bere-provided by the network.

However, an issue arises in a case in which the UE has switched toanother serving cell while in the inactive state (e.g., when the servingcell of the UE during the transition from the inactive state to theconnected state is different from the serving cell of the UE when the UEstored the AS context). For example, as a result of restoring the AScontext based on the AS context stored by the UE, the serving cellcommon configuration configured on the UE may be incorrect. As aparticular example, assume that the UE is in the connected state andthat cell A is the serving cell of the UE. Here, when the UE transitionsto the inactive state, the AS context will include a serving cell commonconfiguration for cell A. In this example, assume that the UE isreselected to cell B while in the inactive state (e.g., such that theserving cell of the UE is cell B rather than cell A). However, when theUE transitions from the inactive state back to the connected state, theUE will restore the stored AS context, meaning that the UE will beconfigured with the serving cell common configuration for cell A, eventhough the serving cell of the UE is cell B. In other words, the servingcell common configuration configured on the UE will be incorrect.

One technique to address this issue is to configure the serving cell toinclude a serving cell common configuration, associated with the servingcell, in the resume message that is received by the UE. In such a case,when the UE transitions from the inactive state back to the connectedstate, the UE will restore the AS context from the AS context stored bythe UE, and will also apply the serving cell common configuration,received in the resume message, to the AS context. However, thistechnique is undesirable since the serving cell is required to send theserving cell common configuration, which increases overhead on thenetwork and signaling overhead over the air interface.

Some aspects described herein provide techniques and apparatuses forcommon channel configuration in an NR inactive state. In some aspects, aUE may receive an RRC resume message, associated with transitioning theUE from an inactive state to a connected state and, based at least inpart on receiving the RRC resume message, may be configured with aserving cell common configuration, associated with a serving cell of theUE, that is received in a SIB (e.g., SIB1) associated with the servingcell. Here, when the RRC resume message includes a serving cell commonconfiguration, the UE is further configured with the serving cell commonconfiguration included in the RRC resume message (e.g., such that theserving cell common configuration included in the RRC resume messageoverwrites the serving cell common configuration received in the SIB).Additional details are provided below.

FIGS. 5A and 5B are diagrams illustrating examples 500 and 550,respectively, of common channel configuration in NR inactive state, inaccordance with various aspects of the present disclosure. Example 500is an example in which an RRC resume message, received by a UE that isto transition from an inactive state to a connected state, does notinclude a serving cell common configuration associated with a servingcell of the UE. Example 550 is an example in which an RRC resumemessage, received by a UE that is to transition from an inactive stateto a connected state, includes a serving cell common configurationassociated with a serving cell of the UE.

In example 500 of FIG. 5A, and as shown by reference number 502, a UE(e.g., UE 120) may be in a connected state in cell A (e.g., a servingcell associated with a base station 110). As shown by reference number504, the UE may be configured, via an RRC reconfiguration messageprovided by cell A, with a serving cell common configuration associatedwith cell A. As shown by reference number 506, in connection with thereconfiguration message, the UE may provide, to cell A, an RRCreconfiguration complete message. At this point, the UE is operating inthe connected state and the UE may communicate with cell A via theestablished RRC connection.

As shown by reference number 508, the UE may receive an RRC releasemessage indicating that the UE session, associated with cell A, is to besuspended, which triggers the UE to transition from the connected stateto an inactive state. In some aspects, the UE may receive such an RRCrelease message when, for example, cell A does not detect activity fromthe UE for a threshold amount of time. As shown by reference number 510,the UE (and cell A) may store an AS context associated with the UE and,as shown by reference number 512, the UE may transition to the inactivestate.

Next, as indicated by reference number 514, mobility of the UE causesthe UE to switch to cell B while the UE is in the inactive state (e.g.,such that the serving cell of the UE switches from cell A to cell B).For example, the UE may be reselected to cell B while the UE is in theinactive state. As another example, the UE may switch to cell B when theUE leaves an area covered by cell A and/or enters an area covered bycell B. As shown by reference number 516, as a result of the switch tocell B, the UE may be configured with a serving cell commonconfiguration, associated with cell B, from a SIB (e.g., SIB1)associated with cell B.

As shown by reference number 518, after the UE switches to cell B whilein the inactive state, the UE may detect a trigger, associated withresuming the session (e.g., when the UE needs to transmit an uplinktransmission, when the UE detects a paging message for the UE, and/orthe like). As shown by reference number 520, the UE can trigger a resumeprocedure, associated with resuming the session, by sending an RRCresume request to cell B (e.g., the current serving cell of the UE).

As shown by reference number 522 a of FIG. 5A, the UE may receive, fromcell B, an RRC resume message, associated with resuming the session,which triggers the UE to transition from the inactive state to theconnected state. Notably, in example 500, the RRC resume message doesnot include a serving cell common configuration associated with cell B.

As shown by reference number 524, based at least in part on receivingthe RRC resume message, the UE restores the AS context (e.g., aspreviously stored by the UE). Additionally, as shown by reference number526 a, a serving cell common configuration, associated with cell B, isconfigured on the UE. As indicated, the serving cell commonconfiguration configured at reference number 526 a is the serving cellcommon configuration received from the SIB associated with cell B (i.e.,the serving cell common configuration received in association withreference number 516). Here, the serving cell common configuration ofcell B will be used by the UE (rather than the serving cell commonconfiguration associated with cell A, which would be configured when theUE restored the AS context). In some aspects, the UE may overwrite theserving cell common configuration restored form the AS context with theserving cell common configuration received in the SIB associated withcell B.

As shown by reference number 528, after configuration of the servingcell common configuration using the serving cell common configurationreceived in the SIB associated with cell B, the UE may provide an RRCcomplete message, and may transition to the connected state.

In example 550 of FIG. 5B, operations associated with reference numbers502 through 520 are similar to those described in association withexample 500 FIG. 5A. However, as shown by reference number 522 b of FIG.5B, the UE may receive, from cell B, an RRC resume message, associatedwith resuming the session, which triggers the UE to transition from theinactive state to the connected state. Notably, in example 550, the RRCresume message includes a serving cell common configuration associatedwith cell B.

As shown by reference number 524, and similar to as described above, theUE restores the AS context (e.g., as previously stored by the UE).Additionally, as shown by reference number 526 b, a serving cell commonconfiguration, associated with cell B, is configured on the UE. Asindicated, by reference number 526 b, the UE may be configured based atleast in part on both the serving cell common configuration receivedfrom the SIB associated with cell B and the serving cell commonconfiguration included in the RRC resume message. As a result, theserving cell common configuration of cell B will be used by the UE(rather than the serving cell common configuration associated with cellA, which would be configured when the UE restored the AS context). Insome aspects, the UE may overwrite the serving cell common configurationrestored from the AS context with the serving cell common configurationreceived in the SIB associated with cell B, and may at least partiallyoverwrite the serving cell common configuration received in the SIB withthe serving cell common configuration included in the RRC resumemessage.

As shown by reference number 528, after configuration of the servingcell common configuration using the serving cell common configurationreceived in the SIB and the serving cell common configuration includedin the RRC resume message, the UE may provide an RRC complete message,and may transition to the connected state.

In this way, the serving cell common configuration configured on the UEwhen the UE transitions from the inactive state to the connected stateis updated (e.g., such that the serving cell common configuration isassociated with a current serving cell of the UE), without requiringadditional signaling overhead (e.g., since cell B need not provide theserving cell common configuration).

As indicated above, FIGS. 5A and 5B are provided as examples. Otherexamples may differ from what is described with respect to FIGS. 5A and5B.

FIG. 6 is a diagram illustrating an example process 600 performed, forexample, by a UE, in accordance with various aspects of the presentdisclosure. Example process 600 is an example where a UE (e.g., UE 120)performs common channel configuration in NR inactive state.

As shown in FIG. 6, in some aspects, process 600 may include receiving aRRC resume message, associated with transitioning the UE from aninactive state to a connected state (block 610). For example, the UE(e.g., using antenna 252, DEMOD 254, MIMO detector 256, receiveprocessor 258, controller/processor 280, and/or the like) may receive aRRC resume message, associated with transitioning the UE from aninactive state to a connected state, as described above.

As shown in FIG. 6, in some aspects, process 600 may includeconfiguring, based at least in part on receiving the RRC resume message,the UE with a serving cell common configuration, associated with aserving cell of the UE, received in a SIB associated with the servingcell (block 620). For example, the UE (e.g., using antenna 252, DEMOD254, MIMO detector 256, receive processor 258, controller/processor 280,and/or the like) may configure, based at least in part on receiving theRRC resume message, the UE with a serving cell common configuration,associated with a serving cell of the UE, received in a SIB associatedwith the serving cell, as described above.

Process 600 may include additional aspects, such as any single aspectand/or any combination of aspects described below and/or in connectionwith one or more other processes described elsewhere herein.

In a first aspect, when the RRC resume message includes a serving cellcommon configuration, the UE is further configured with the serving cellcommon configuration included in the RRC resume message. Here, theserving cell common configuration included in the RRC resume messageoverwrites the serving cell common configuration received in the SIB.

In a second aspect, alone or in combination with the first aspect, theRRC resume message does not include a serving cell common configuration.

In a third aspect, alone or in combination with any one or more of thefirst and second aspects, the UE is further configured based at least inpart on an access stratum (AS) context stored on the UE before enteringthe inactive state.

In a fourth aspect, alone or in combination with any one or more of thefirst through third aspects, the UE is configured with the serving cellcommon configuration received in the SIB instead of being configuredwith a serving cell common configuration included in the AS context.That is, in the fourth aspect, the UE is configured with the servingcell common configuration received in the SIB instead of using a servingcell common configuration from a serving cell of the UE when the UEentered the inactive state

In a fifth aspect, alone or in combination with any one or more of thefirst through fourth aspects, the SIB, associated with the serving cell,is received based at least in part on UE mobility that causes the UE tobe served by the serving cell while the UE is in the inactive state.

In a sixth aspect, alone or in combination with any one or more of thefirst through fifth aspects, the SIB, associated with the serving cell,is SIB1 associated with the serving cell.

In a seventh aspect, alone or in combination with any one or more of thefirst through sixth aspects, the RRC resume message is received inconnection with a RRC resume request being provided. Here, the RRCresume request is provided based at least in part on detection of atrigger to transition the UE from the inactive state to the connectedstate.

In an eighth aspect, alone or in combination with any one or more of thefirst through seventh aspects, the UE transitions to the connected statefrom the inactive state after configuration of the UE with the servingcell common configuration received in the SIB.

Although FIG. 6 shows example blocks of process 600, in some aspects,process 600 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 6.Additionally, or alternatively, two or more of the blocks of process 600may be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the aspects to the preciseform disclosed. Modifications and variations may be made in light of theabove disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, and/or a combination of hardware and software. Asused herein, a processor is implemented in hardware, firmware, and/or acombination of hardware and software.

Some aspects are described herein in connection with thresholds. As usedherein, satisfying a threshold may refer to a value being greater thanthe threshold, greater than or equal to the threshold, less than thethreshold, less than or equal to the threshold, equal to the threshold,not equal to the threshold, and/or the like.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, and/or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the aspects. Thus, the operation and behavior of thesystems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based, at leastin part, on the description herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various aspects. In fact, many ofthese features may be combined in ways not specifically recited in theclaims and/or disclosed in the specification. Although each dependentclaim listed below may directly depend on only one claim, the disclosureof various aspects includes each dependent claim in combination withevery other claim in the claim set. A phrase referring to “at least oneof” a list of items refers to any combination of those items, includingsingle members. As an example, “at least one of: a, b, or c” is intendedto cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combinationwith multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c,a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering ofa, b, and c).

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the terms “set” and “group” are intended to include oneor more items (e.g., related items, unrelated items, a combination ofrelated and unrelated items, and/or the like), and may be usedinterchangeably with “one or more.” Where only one item is intended, thephrase “only one” or similar language is used. Also, as used herein, theterms “has,” “have,” “having,” and/or the like are intended to beopen-ended terms. Further, the phrase “based on” is intended to mean“based, at least in part, on” unless explicitly stated otherwise.

What is claimed is:
 1. A method of wireless communication performed by auser equipment (UE), comprising: obtaining an access stratum (AS)context comprising a first serving cell common configuration associatedwith a first cell while the UE is in a connected state; receiving asystem information block (SIB) associated with a second cell inconnection with the UE switching to the second cell, the SIB including asecond serving cell common configuration for the second cell; receivinga radio resource control (RRC) resume message, associated withtransitioning the UE from an inactive state to the connected state,separately from receiving the SIB; and configuring, based at least inpart on receiving the RRC resume message, the UE with the second servingcell common configuration received in the SIB.
 2. The method of claim 1,wherein, when the RRC resume message includes a third serving cellcommon configuration, the UE is further configured with the thirdserving cell common configuration included in the RRC resume message,wherein the third serving cell common configuration included in the RRCresume message overwrites the second serving cell common configurationreceived in the SIB.
 3. The method of claim 1, wherein the RRC resumemessage does not include a serving cell common configuration.
 4. Themethod of claim 1, wherein the UE is further configured based at leastin part on the AS context obtained by the UE before entering theinactive state.
 5. The method of claim 1, wherein the UE is configuredwith the second serving cell common configuration received in the SIBinstead of using the first serving cell common configuration obtainedfrom the first cell.
 6. The method of claim 1, wherein the SIB,associated with the second cell, is received based at least in part onUE mobility that causes the UE to reselect to the second cell.
 7. Themethod of claim 1, wherein the SIB, associated with the second cell, isSIB1 associated with the second cell.
 8. The method of claim 1, whereinthe RRC resume message is received in connection with a RRC resumerequest being sent by the UE, wherein the RRC resume request is sent bythe UE based at least in part on detection of a trigger to transitionthe UE from the inactive state to the connected state.
 9. The method ofclaim 1, wherein the UE transitions to the connected state from theinactive state after configuration of the UE with the second servingcell common configuration received in the SIB.
 10. A user equipment (UE)for wireless communication, comprising: a memory; and one or moreprocessors coupled to the memory, the memory and the one or moreprocessors configured to: obtain an access stratum (AS) contextcomprising a first serving cell common configuration associated with afirst cell while the UE is in a connected state; receive a systeminformation block (SIB) associated with a second cell in connection withthe UE switching to the second cell, the SIB including a second servingcell common configuration for the second cell; receive a radio resourcecontrol (RRC) resume message, associated with transitioning the UE froman inactive state to the connected state, separately from receiving theSIB; and configure, based at least in part on receiving the RRC resumemessage, the UE with the second serving cell common configurationreceived in the SIB.
 11. The UE of claim 10, wherein, when the RRCresume message includes a third serving cell common configuration, theUE is further configured with the third serving cell commonconfiguration included in the RRC resume message, wherein the thirdserving cell common configuration included in the RRC resume messageoverwrites the second serving cell common configuration received in theSIB.
 12. The UE of claim 10, wherein the RRC resume message does notinclude a serving cell common configuration.
 13. The UE of claim 10,wherein the UE is further configured based at least in part on the AScontext obtained by the UE before entering the inactive state.
 14. TheUE of claim 10, wherein the UE is configured with the second servingcell common configuration received in the SIB instead of using the firstserving cell common configuration obtained from the first cell.
 15. TheUE of claim 10, wherein the SIB, associated with the second cell, isreceived based at least in part on UE mobility that causes the UE toreselect to the second cell.
 16. The UE of claim 10, wherein the SIB,associated with the second cell, is SIB1 associated with the secondcell.
 17. The UE of claim 10, wherein the RRC resume message is receivedin connection with a RRC resume request being sent by the UE, whereinthe RRC resume request is sent by the UE based at least in part ondetection of a trigger to transition the UE from the inactive state tothe connected state.
 18. The UE of claim 10, wherein the UE transitionsto the connected state from the inactive state after configuration ofthe UE with the second serving cell common configuration received in theSIB.
 19. A non-transitory computer-readable medium storing one or moreinstructions for wireless communication, the one or more instructionscomprising: one or more instructions that, when executed by one or moreprocessors of a user equipment (UE), cause the one or more processorsto: obtain an access stratum (AS) context comprising a first servingcell common configuration associated with a first cell while the UE isin a connected state; receive a system information block (SIB)associated with a second cell in connection with the UE switching to thesecond cell, the SIB including a second serving cell commonconfiguration for the second cell; receive a radio resource control(RRC) resume message, associated with transitioning the UE from aninactive state to the connected state, separately from receiving theSIB; and configure, based at least in part on receiving the RRC resumemessage, the UE with the second serving cell common configurationreceived in the SIB.
 20. The non-transitory computer-readable medium ofclaim 19, wherein, when the RRC resume message includes a third servingcell common configuration, the UE is further configured with the thirdserving cell common configuration included in the RRC resume message,wherein the third serving cell common configuration included in the RRCresume message overwrites the second serving cell common configurationreceived in the SIB.
 21. The non-transitory computer-readable medium ofclaim 19, wherein the RRC resume message does not include a serving cellcommon configuration.
 22. The non-transitory computer-readable medium ofclaim 19, wherein the UE is further configured based at least in part onthe AS context obtained by the UE before entering the inactive state.23. The non-transitory computer-readable medium of claim 19, wherein theUE is configured with the second serving cell common configurationreceived in the SIB instead of using the first serving cell commonconfiguration obtained from the first cell.
 24. The non-transitorycomputer-readable medium of claim 19, wherein the SIB, associated withthe second cell, is received based at least in part on UE mobility thatcauses the UE to reselect to the second cell.
 25. The non-transitorycomputer-readable medium of claim 19, wherein the SIB, associated withthe second cell, is SIB1 associated with the second cell.
 26. Thenon-transitory computer-readable medium of claim 19, wherein the RRCresume message is received in connection with a RRC resume request beingsent by the UE, wherein the RRC resume request is sent by the UE basedat least in part on detection of a trigger to transition the UE from theinactive state to the connected state.
 27. The non-transitorycomputer-readable medium of claim 19, wherein the UE transitions to theconnected state from the inactive state after configuration of the UEwith the second serving cell common configuration received in the SIB.28. An apparatus for wireless communication, comprising: means forobtaining an access stratum (AS) context comprising a first serving cellcommon configuration associated with a first cell while the apparatus isin a connected state; means for receiving a system information block(SIB) associated with a second cell in connection with the apparatusswitching to the second cell, the SIB including a second serving cellcommon configuration for the second cell; means for receiving a radioresource control (RRC) resume message, associated with transitioning theapparatus from an inactive state to the connected state, separately fromreceiving the SIB; and means for configuring, based at least in part onreceiving the RRC resume message, the apparatus with the second servingcell common configuration received in the SIB.
 29. The apparatus ofclaim 28, wherein the RRC resume message does not include a serving cellcommon configuration.
 30. The apparatus of claim 28, wherein theapparatus is configured with the second serving cell commonconfiguration received in the SIB instead of being configured with thefirst serving cell common configuration included in the AS contextobtained by the apparatus before entering the inactive state.